|
|
|
|
|
|
|
Finally, you can cloak projects to aid in parallel development. To cloak a project means that you're not interested in a particular project. Thus, cloaking such a project means that its files are not copied to your local file structure. For instance, if you check out or get a copy of the master project and its subprojects, each subproject that is cloaked will not be copied to your hard disk. This is especially helpful for cloaking projects you don't own as a developer; you don't know what state a foreign subproject is in, so there's no need to access the files in it. |
|
|
|
|
|
|
|
|
To cloak a project, first create a subproject called Subsystem1 under the Increment1 subproject of the First Iteration project. Select the Subsystem1 subproject by clicking on it. Choose File|Properties from the menu. Click the This Project Is Cloaked for Me check box to cloak a project you don't own (see Figure 8.9). Click the Close button. Notice that the Subsystem1 project folder icon is now dimmed. |
|
|
|
|
|
|
|
|
Figure 8.9.
Click the This Project Is Cloaked for
Me check box to cloak a project you
don't own. |
|
|
|
|
|
|
|
|
Local Directory Structuring |
|
|
|
|
|
|
|
|
Every project you create in SourceSafe, or at least every project that you own as a developer on a team, will need a corresponding working directory on your hard disk. In general, you can create any local working folder on your hard disk as you deem necessary. However, a good rule of thumb is to name your local folder with the same name as the corresponding project folder in SourceSafe. |
|
|
|
|
|
|
|
|
Nonetheless, you don't have to have the exact same hierarchy unless you have a SourceSafe server dedicated to your individual subsystem or component projects. You only need to create corresponding local folders for each SourceSafe project folder you own. For instance, because you cloaked the Subsystem1 folder earlier, you would not need to create a local folder named Subsystem1. |
|
|
|
|
|
